Generalized keyword expression syntax sugar #67
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previously arguments were additional properties at the top level of the keyword expression object (siblings of the `0` property). Now they are packed into a single property value keyed by `1`. This brings keyword expressions semantics closer to function semantics (both now have a single argument), and will help make the upcoming generalized keyword expression syntax sugar more sensible.
This carves out syntax space for a planned generalized keyword expression sugar (`@` will become relevant to parsing).
mkantor
force-pushed
the
generalized-keyword-expression-sugar
branch
from
fbdcc31 to
7fef85a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Any keyword expression can now be written using the following syntax sugar:
This is especially helpful for
@if, which felt quite awkward.Previously, you'd write this:
Now, it's this:
(Keys are optional, as they were before.)